api/src/main/java/io/minio/MinioAsyncClient.java (1)

1120-1139: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Avoid recursive hasNext() now that NoSuchVersion-only batches continue.

With completed = error != null, many consecutive all-NoSuchVersion batches now flow into return hasNext(); (Line 1139), which can recurse per batch and eventually overflow the stack on large inputs. Switch this tail-recursive path to a loop.

💡 Proposed fix

           `@Override`
           public boolean hasNext() {
-            while (error == null && errorIterator == null && !completed) {
-              populate();
-            }
-
-            if (error == null && errorIterator != null) setError();
-            if (error != null) return true;
-            if (completed) return false;
-
-            errorIterator = null;
-            return hasNext();
+            while (true) {
+              while (error == null && errorIterator == null && !completed) {
+                populate();
+              }
+
+              if (error == null && errorIterator != null) setError();
+              if (error != null) return true;
+              if (completed) return false;
+
+              errorIterator = null;
+            }
           }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@api/src/main/java/io/minio/MinioAsyncClient.java` around lines 1120 - 1139,
The hasNext() implementation in MinioAsyncClient now recurses through repeated
all-NoSuchVersion batches via the final return hasNext() path, which can grow
the call stack on large inputs. Replace that tail-recursive fallback in
hasNext() with an explicit loop that keeps advancing until error, completion, or
a non-empty errorIterator is found, while preserving the current populate() and
setError() behavior.